/stopsectionlevel for sectioning commands
instead. That way, users could add \definesectionlevels to the document
preamble to use whatever sectioning scheme they wanted. However, this
would mean that the exporter wouldn't know what sectioning commands to
use the TOC setup.
given the amount of reactions i
ntent]
> [list={section,subsection}]
> for n=2.
>
> I'm considering using \start/stopsectionlevel for sectioning commands
> instead. That way, users could add \definesectionlevels to the document
> preamble to use whatever sectioning scheme they wanted. However, this would
&
ection)
will translate into a definesectionlevels command and inform your
exporter about the used sectionlevels. Once the used commands are known
it should be possible to map toc:2 to a combinedlist definition.
I can't require the user to use more do
toc:2.
This:
#+Context_Section_Levels: '(chapter section subsection)
will translate into a definesectionlevels command and inform your
exporter about the used sectionlevels. Once the used commands are known
it should be possible to map toc:2 to a combinedlist defi
On 12/24/21 1:29 PM, Denis Maier wrote:
I probably wasn't clear. You will support toc:2.
This:
#+Context_Section_Levels: '(chapter section subsection)
will translate into a definesectionlevels command and inform your
exporter about the used sectionlevels. Once the used commands are known
upport "toc:2".
I probably wasn't clear. You will support toc:2.
This:
#+Context_Section_Levels: '(chapter section subsection)
will translate into a definesectionlevels command and inform your exporter about the used sectionlevels. Once the used commands are know
ontent]
[list={section,subsection}]
for n=2.
I'm considering using \start/stopsectionlevel for sectioning commands
instead. That way, users could add \definesectionlevels to the document
preamble to use wh
ld add \definesectionlevels to the document
preamble to use whatever sectioning scheme they wanted. However, this
would mean that the exporter wouldn't know what sectioning commands to
use the TOC setup.
Thanks,
add \definesectionlevels to the document
preamble to use whatever sectioning scheme they wanted. However, this
would mean that the exporter wouldn't know what sectioning commands to
use the TOC setup.
Thanks,
Jason
to
subsubsubsubsection), you may need to define your own using
\definesectionlevels.
Best regards
Andreas
Am 2016-03-11 09:08, schrieb m...@silentumbrella.com:
Greetings,
Is it possible to have
\starttext
\startchapter
Hey a chapter!
\startsection
something.one
\startsection
someting.one.one
or
\startsubsubsection …
You’re looking for the \startsectionlevel command.
%\definesectionlevels[default][part,chapter,section,subsection]
\starttext
\completecontent[criterium=all]
\startsectionlevel[title=Colors,reference=colors]
\startsectionlevel[title=Black,reference=black]
black
Quoting from the thread Adaptive section structuring of September
2012:
%\definesectionlevels[default][section,subsection,subsubsection]
\definesectionlevels[mine][title,subject,subsubject]
\starttext
\startsectionlevel [title=Alpha]
\startsectionlevel [title=Beta
!
This is exactly what I was looking for. Due to this I also found \currentstructurereference and a bunch of other commands :)
Once you know that "structure" is the keyword, "strc-sec.*" is just around the corner.
Regarding your earlier mail (\definesectionlevels ...):
Wow, t
(that will print a list) should also add a heading. However, the
heading should always be one level beneath the current heading and without
numbering. Example: within a \section it should be a \subsubject, within a
\chapter it should be a \subject, and so on.
\definesectionlevels[extra
and normal section command. When you want a \section
for the first level change the level settings with
\definesectionlevels
[default]
[section,
subsection,
subsubsection,
subsubsubsection,
subsubsubsubsection]
and use
\starttext
\startsectionlevel[title=Section]
\startsectionlevel[title
15 matches
Mail list logo
